home *** CD-ROM | disk | FTP | other *** search
Text File | 1987-11-21 | 5.6 KB | 135 lines | [TEXT/MACA] |
-
- LightspeedC v2.13
- Release Notes
- 11/9/87
-
- Version 2.11 corrected some compatiblity problems related to new Apple
- hardware and software, and supplied preliminary interfaces to the new
- ROM calls. This version adds MultiFinder compatibility, and updates
- the interfaces to their final form.
-
- The upgrade is provided in the form of a patch program, new #include
- files, and new libraries. It is not necessary to recompile any code
- after upgrading, but you should remember to load the new libraries.
-
-
- About the patch program
- -----------------------
-
- The patch program, "Patch LSC => 2.13", transforms your version 2.01
- or 2.11 into version 2.13. You are prompted for a file containing the
- copy of LightspeedC to be patched. Patch a copy, not your original!
- If the patch program encounters an error, the LightspeedC being patched
- may not be left in a consistent state, so start again with a fresh copy.
-
-
- About the #include files
- ------------------------
-
- The #include files supplied with this release completely replace the
- existing Mac #includes. The preliminary "x..." files supplied with
- the 2.11 release have been updated and consolidated into the mainstream
- set of #includes.
-
- For the most part, the organization of the #include files follows that
- of Inside Macintosh. However, some chapters have been combined. The
- file "Color.h" corresponds to the "Color Quickdraw", "Graphics Devices",
- "Color Manager", "Palette Manager", and "Color Picker Package" chapters
- of Volume V. Data structures describing the color extensions to the
- Control Manger, Menu Manager, and Window Manager have been combined as
- "ColorToolbox.h". Finally, interfaces to SysEnvirons, the Deferred Task
- Manager, and the ShutDown Manager appear in "OSUtil.h".
-
-
- About the libraries
- -------------------
-
- The "PrLink.Lib" library is no longer distributed. Print Manager
- interfaces are now contained in "MacTraps".
-
- The "Appletalk.Lib" library and its accompanying resource file, "ATalk/
- ABPackage", are no longer distributed. They have been replaced by a
- new library, "Appletalk". Additional Appletalk interfaces are contained
- in "MacTraps". See "About Appletalk", below, for more information.
-
- "MacTraps" has gotten larger in this release. This is due in part to
- the incorporation of Print Manager and Appletalk interfaces, and in part
- to other new interfaces described in Volume V of Inside Macintosh. In
- addition, the new "MacTraps" contains a great deal more information for
- use by the "smart" linker. This means that "Build" is able to strip
- away a greater amount of unused code than before. When you "Build"
- your projects with version 2.13, you may find that they get smaller!
-
-
- About MultiFinder
- -----------------
-
- When MultiFinder is in use, the "Run" and "Transfer" commands do not
- cause LightspeedC to exit. (It is not possible to quit LightspeedC while
- a project is running.)
-
- In general, two megabytes of memory are required to use LightspeedC
- with MultiFinder. However, it may be feasible to develop very small
- projects in only one megabyte by reducing LightspeedC's size requirements
- using the Finder's "Get Info" command. It is also necessary to install
- a 'SIZE',0 resource in the project document, to get the project to run
- in a small partition.
-
-
- About "sub-launching"
- ---------------------
-
- Apple Technical Note #126 describes "sub-launching". Under MultiFinder,
- it is possible to launch an application without exiting. For technical
- reasons, though, it is difficult to use this feature in LightspeedC. So
- the new "MacTraps" library defines a function to do it for you:
-
- extern int SubLaunch(char *appl, int fdFlags);
-
- The first argument, "appl", is a pascal string giving the name of the
- program to launch. It is up to you to set the current directory (using
- SetVol) before calling SubLaunch. The second argument, "fdFlags", is
- the flags word from the finder information record (FInfo); it can be
- obtained by calling GetFInfo. (See Tech Note #126 for details.) A
- negative return result from SubLaunch indicates that the attempt failed;
- any other result indicates success.
-
- WARNING: If bit 6 (0x0040) is set in "fdFlags", MultiFinder will ignore
- the various flag bits in the application's SIZE resource. These bits
- determine whether the application is "MultiFinder-aware" and whether it
- is to receive suspend/resume events and background null events. Apple
- has acknowledged this as a bug in MultiFinder 1.0. We recommend always
- passing 0 for "fdFlags".
-
-
- About Appletalk
- ---------------
-
- There are now two sets of Appletalk interfaces, which Apple calls the
- "preferred" set and the "alternate" set. Either or both may be used.
-
- The original Appletalk calls introduced in Volume II of Inside Macintosh
- are now considered the "alternate" set. The new, "preferred" calls appear
- in Volume V of Inside Macintosh.
-
- Until this release, Appletalk interfaces were provided in the form of
- a library, "Appletalk.Lib", and a resource file, "ATalk/ABPackage".
- These have now been consolidated into a single library, "Appletalk".
- This library constitutes the "alternate" set. The #include file
- "Appletalk.h" defines data structures necessary when using these calls.
-
- Interfaces to the "preferred" set are contained in "MacTraps". The
- #include file "nAppletalk.h" defines data structures necessary when
- using these calls.
-
- The above information is summarized in the following table:
-
- "preferred" "alternate" 2.01/2.11
-
- interface code: MacTraps Appletalk Appletalk.Lib
- #include file: nAppletalk.h Appletalk.h Appletalk.h
- resource file: (n/a) (n/a) ATalk/ABPackage
-
- Remember, if you are using only the "preferred" calls, there is no need
- to load the "Appletalk" library into your project.